Night Owl 6/Night Owl's Shareware - PDSI-006 - Night Owl Corp (1990).iso/001a/rbx23.zip/RBX.DOC

Text File | 1991-01-03 | 17KB | 417 lines

                               RBX

                        Read BIX Messages
                           Release 2.3
                          1 January 1991


                      MICROCode Consulting
                            Box 9001
                        Torrance CA 90503

                      [phone] Voice
               [phone] Data (300/1200/2400)


                       DISTRIBUTION RIGHTS

The right to distribute this document and related software is
granted to the extent stated herein.  No other rights are granted
or implied.

This document describes RBX, a program for reading Byte
Information Exchange (BIX) conference messages.  Included with
this document are binary executable codes.  The document and
binary executable codes are hereafter designated as Contents.
(BIX is a trademark of McGraw-Hill, Inc.)

MICROCode Consulting hereby grants that Contents is released for
unlimited distribution.  Contents may be given, transmitted,
reproduced and utilized without charge excepting the actual cost
of reproduction.  Contents may not be included in any
commercial  or for-profit package without the express written
permission of MICROCode Consulting.


COPYRIGHT (C) 1988,  1989, 1990, 1991 MICROCode Consulting.  All
rights reserved.

                           DISCLAIMER

MICROCode Consulting makes no representations or warranties
with respect to the contents hereof and related software and
specifically disclaims any implied warranties of merchantibility
or fitness for any particular purpose.  Further, MICROCode
Consulting reserves the right to revise the software and the
contents hereof without the obligation of MICROCode Consulting
to notify any person of such revision or changes.



         RBX  (C) 1988, 1989, 1990, 1991 MICROCode Consulting


                        TABLE OF CONTENTS

A.  Introduction
B.  Getting Started
C.  Downloading messages from BIX
D.  Executing RBX
E.  Uploading message replies to BIX


A.  Introduction


RBX is a program intended to operate in conjunction with the
Byte Information Exchange (BIX) to facilitate browsing of
conference messages.  RBX was designed to work with your local
computer system to help reduce your connection costs while
providing a single-keystroke full screen interface to the BIX
message base.  Major features include:

   - display messages one at a time on screen.  All commands are
     single keystroke to simplify operation
   - read messages sequentially or "follow the message thread"
   - back up through messages in same order as read
   - skip entire conference topics to read later or just delete
     them with a couple keystrokes
   - save specific messages for later reading
   - save specific messages to a disk file
   - skip entire message threads
   - send followup message (builds upload file for BIX)
   - join specific conf/topic
   - search messages in specific conference topic for string
     (case insensitive, wild characters accepted)
   - read messages in a specific BIX file

Using BIX with RBX is straightforward.  First, one connects to
BIX to retrieve all new messages in the subscribed conferences
as discussed in Section C.  After disconnecting from BIX, RBX is
executed to read some or all messages as described in Section D.
Finally, one can upload any comments to BIX messages created by
RBX as described in Section E.


B.  Getting Started


Before charging off to use RBX, you should prepare a new floppy
disk (or have sufficient space on your hard drive).  If you
belong to many conferences and connect with BIX at long
intervals, it is not difficult to find between 60k and 600k of
messages to be downloaded.

RBX inherently works with three files on your disk:

CONF.BIX   Any messages that were not read during the last
           session of RBX are saved in this file.  If no
           messages are saved, this file will not exist.

FROM.BIX   This is the file containing the most recent download
           of messages from BIX.  See Section C for more details.

TO.BIX     This file is created by RBX and contains your comments
           (replies) to messages.  This file should be sent to
           BIX on your next connection and deleted afterwards as
           described in Section E.


RBX can also work with any user-named file with or without an
extension of ".BIX".  Section D contains more detail.

There a several binary versions of RBX completed.  Choose the
correct one for your system:

     RBX.CPM   For any Xerox, Kaypro or similar computer
     RBX.ZIP   For any IBM-PC or true clone
     RBX.SUN   For any SUN Microsystems UN*X machine

Others may be added as the program is modified for other
hardware platforms.

RBX.ZIP contains the following files:

        RBX.EXE         Executable for your system
        RBX.CFG         Your personal preferences file
        RBX.DOC         This file (hopefully)
        RBXERR.MSG      Text file containing error messages
                        used by RBX

RBX.CFG is the configuration file for RBX, which selects
important features such as screen size, colors, etc.  RBX.CFG is
thoroughly documented internally, and that information is not
repeated here.  If you are missing any of these files, log onto
BIX and get a fresh copy of RBX.ZIP from the MICROCode
conference.


C.  Downloading messages from BIX


Retrieving messages from BIX into a single file called FROM.BIX
is the first step towards using RBX.  To do so, you will need to
connect to BIX.

If you are an avid BIXer or call in at frequent intervals, you
will probably prefer to download all pending messages at once
using your communications program's fastest protocol.  You
should set this protocol within your PROFILE using the OPT
command.  See your BIX users manual for information on editing
the PROFILE.

With the protocol set and connected to BIX at the ":" prompt,
one should  first clear the scratchpad by typing:

     clear

In order to retrieve the conference messages, one must first
join a conference.  The simplest way is by pressing RETURN at
the ":" prompt; BIX will join any active conference (one with
messages pending).  If there are no new messages, BIX will
inform you of such and return to the ":" prompt.  Otherwise,
typing

     file all

will copy new messages from all subscribed conferences to the
scratchpad.  (BIX limits the size of the scratchpad.  Currently
it is 2 Megabytes.  Any messages which exceed this limit during
a "file all" operation are lost.)  Once that is completed, type

     download

and BIX is awaiting protocol connection to your communications
program.  Instruct your local communications program to receive
the file and label it "FROM.BIX".


D.  Executing RBX


With a file of conference messages from BIX to read (or unread
messages left from your last session), RBX is ready for use.
Ensure that "CONF.BIX" (if it exists) and "FROM.BIX" (if it
exists) are in the current directory.

With the "*.BIX" files on the current drive, you are ready to
proceed.  There are two ways to execute RBX: default mode or
specific BIX file.  The default mode of executing RBX is
accomplished by typing:

     RBX

After signing on, RBX will scan "CONF.BIX" for any previous
messages and "FROM.BIX" for any new messages.  Although one
might not have both files, at least one should exist.  If
neither of these files exist, RBX will exit explaining the lack
of messages to read.  RBX first builds its internal tables of
message locations, numbers, and the thread to which each
belongs. Once that is complete, RBX is ready for user input.

If a specific file of BIX messages has been saved under another
name, RBX can be directed to use that file by entering:

     RBX bixfile

where "bixfile" is any file name with or without a filename
extension.  However, if no filename extension is supplied, RBX
will assume ".BIX".

When the filename is privided, RBX uses this file and this file
ONLY.  This alternative method is useful for revisiting a set
of BIX messages that were saved under a particular topic.

After scanning the appropriate file(s), RBX visits each active
conference/topic in order indicating the number of new messages.
One can either read messages (space bar or "Y"es), skip for now
("N"), mark all messages in this conference/topic as read
("C"atch up), or exit RBX ("Q"uit).

Rather than bore you with all the possible commands within RBX,
use the HELP key (either a "?" or "H" will bring up the help
menu) at any point in  the program.  RBX will respond in one of
two ways:

     - You will get a glorious help screen detailing every
       possible command that can be used at this point.

     - You will get nothing.  This only occurs when the help key
       is not very helpful (only a simple YES or NO question was
       asked) or the help key would interfere with normal
       operation (as when sending replies to messages).

You can pretty much use RBX without ever pressing another key
other than the SPACE BAR.  (The SPACE BAR is treated the same
as the "Y" key in RBX.)

Some highlights of RBX operation are listed on the following
pages.  In particular, some subtle features are discussed.

RBX can either read messages in forward order (using the "I"n
order key) or in message thread order (using the "R"eference
key).  The default mode of RBX is "Read by Reference" or follow
the thread.  One can change the method at any time while reading
messages.

As you read a message in any conference/topic, it is marked as
read.  You can manipulate any message, marked or not, to do such
things as read or reply.  However, RBX will not visit a
previously read message unless explicitly instructed.  All read
messages are deleted when RBX exits unless RBX is directed
otherwise.

To revisit messages within the current conference/topic, you may
back up one message by pressing the (-) key, or enter the
desired message number.  To revisit messages in another
conference/topic you must first join that conference/topic.

The "J"oin command is similar to its BIX counterpart.  If you
enter an  invalid or partial conference/topic name, RBX will
search and list all  conference/topics which match the partial
name entered; it will then prompt  again for the
conference/topic name.  This is useful if you cannot remember
the exact conference/topics.

If a specific conference/topic does not contain any messages in
the current  file, it will not be indicated as an active topic
by RBX. Also, if all  messages in the conference/topic have been
marked as read during the  current session, it will no longer be
visible.  However, you may still join  the conference/topic to
manipulate (unmark and comment to) messages.

RBX can save a message to a file.  This feature is used to
retain messages for reference at some future date.  RBX uses the
conference name to construct a filename for saving the message,
or you may reject the default and  provide your own filename to
be written.  When saving a message, RBX will append the message
to the end of an existing file.  Otherwise, a new file is
created.


RBX also has a search facility for locating messages containing
a specific  string in a given conference/topic.  Case is ignored
during the search and "?" is treated as a wildcard (e.g. any
character matches a "?" in the  search string).  RBX will stop
at the first unread message which matches the string; the
search string is retained as the default string for future
searches.

After you have finished reading any conference messages, any
unmarked (unread) messages are written to "CONF.BIX" (or back to
the user specified bix file).  RBX gets your permission before
updating it.

For default RBX execution, it does not matter in which file -
"FROM.BIX" or  "CONF.BIX" - the messages originally resided;
they will be written to  "CONF.BIX".  "FROM.BIX" is deleted
after this is completed in anticipation  of your next download
from BIX.  Again, RBX gets your permission before  updating
"CONF.BIX" and deleting "FROM.BIX".


E.  Uploading message replies to BIX


Whenever you make written comments to BIX messages using RBX, a
file named  "TO.BIX" is either created or extended to include
the new replies.  This file is preset with commands for sending
comments to messages on BIX  itself.  The "TO.BIX" file is plain
text, so you may edit it before sending it if you wish.

Before sending the file, you should connect with BIX and clear
your  scratchpad.  Clearing the scratchpad is accomplished by
typing:

     clear

At this point, use your communications program to send the file
as TEXT  (NOT a special protocol transfer).  "TO.BIX" contains
commands for joining  the conference/topic and commenting to
messages as well as the text of the replies.  You will be able
to watch this activity on your screen.

Once the file has been sent to BIX, your comments are now part
of the BIX  system.  When you return to your local computer
system, you must delete "TO.BIX".  (RBX does not know which
comments, if any, have actually been  uploaded.  Therefore, it
will either append new comments to the end of "TO.BIX" or create
a new file if "TO.BIX" does not exist.)

The reply system in RBX shells to your favorite editor
(specified in  RBX.CFG) because familiarity with your favorite
editor is of greater practical use than the lack of
yet-another-editor which could be offered in RBX.  If no editor
has been set, some RBX versions fall back to simple single-line
prompting (yawn!) for each reply line.  This should "encourage"
use of your own editor.


Answers to Common questions/problems:


- RBX was deliberately designed to be simple to use and implement.
  There is no end to nice features we'd like to add, but there are
  other packages available which are full featured and
  consequently take more time to set up and use.  Our prime
  objective was zero set-up time.

- RBX 2.3 for the PC and Clones is compiled with Turbo C 2.0. If
  your computer has any problems with Turbo C (I know of none)
  then it would have problems with RBX 2.3.  (RBX 1.0 used MIX C
  and had I/O problems on some systems.)

- RBX 2.3 for the PC and clones no longer requires that ANSI.SYS
  be loaded.  In fact, it totally ignores any ANSI.SYS (loaded or
  not!).  It does assume that your PC is compatible at the BIOS
  level.  If not, let us know.  Sufficient demand for BIOS
  incompatible PCs will encourage us to offer yet another version.

- RBX uses the BIX character count (which is SELDOM accurate) at
  the beginning of the message to estimate the end of the
  message.  If you encounter a "fatal error", this means that the
  file contains a series of exactly ten (or twenty) equal (====)
  signs, starting at the left column, which is at or near the
  point where BIX *claims* that the message has ended.  RBX is
  hopelessly confused.  You should modify the "FROM.BIX" file
  with your favorite editor so that RBX can find and parse the
  headers.  Fortunately, this does not happen TOO often.

- RBX works with either terse or verbose message headers.  You
  can save a small bit of download time by adding

     opt terse q

  to your user profile.

- Carefully set your ASCII upload settings so that your comments
  are not double-spaced.  If your comm program replaces CR with a
  CR-LF sequence, your CR and LF will be seen by BIX as two
  seperate newline characters.  This makes for funny-looking
  messages.


- For editing your comments, you should avoid editor modes which
  set the high-bit (such as Wordstar document mode).

- RBX 2.3 may be available on request for CP/M and UNIX (SUN)
  platforms.  Leave a message in the MICROCode conference.
  (Didn't have much feedback for these last time.)

- There is a 2000-message limit on the size of the CONF.BIX and
  any other archive BIX file.  (FROM.BIX is read on the fly using
  the assumption that you went to Nepal for a while, so
  there is no limit.)  The CP/M version is limited to 1200
  messages.

- The percentage of the message viewed may be erroneously
  reported as negative if the message is huge (40K bytes or
  larger).  Well, maybe it isn't an error.  Any message that long
  (program listings aside) should be viewed negatively.

- If (when) the BIX character count is grossly inaccurate,
  messages are occasionally concatenated.